home *** CD-ROM | disk | FTP | other *** search
Text File | 1990-06-29 | 1.6 KB | 51 lines | [TEXT/GEOL] |
- Item forwarded by NOVELL.MAC to NOVELL.ENG
-
- Item 9710470 29-June-90 11:02PDT
-
- From: X1783 Stross, Kenner,VCA
-
- To: V0683 Amoco Tech, Eric Berdahl,VAR
-
- cc: CPLUS.DEV$ C++ Interest List--Developers
- MACAPP.TECH$ MacApp Technical
- X1783 Stross, Kenner,VCA
-
- Sub: Re[2] How to debug C++/MacApp
-
- Eric,
-
- Thanks for the prompt response. I am still a little mystified, though. You
- say you haven't had a problem with PascalObjects (MacApp descendents).
- However, those are exactly the type I am having a problem with. Here are the
- approximate details (from memory):
-
- class TMyGridView : public TTextGridView
- {
- virtual pascal void AdornCol (rect *area)
- };
-
- pascal void TMyGridView::AdornCol (rect *area)
- {
- EnterMacAppDebugger ();
- .
- .
- .
- }
-
- The reason that I've hard coded the EnterMacAppDebugger is that the debugger
- fails to break on the routine when I set a breakpoint on TMyGridView.AdornCol.
- I tried TMyGridView::AdornCol and TMyGridView:AdornCol - it rejected both of
- those.
-
- Now here's the interesting part: When I break into the debugger and do a stack
- crawl with the 'S' command, it thinks that I'm in TGridView.Draw (which is the
- last Pascal method to have been called before my C++ virtual function). This
- is what I mean about the debugger not having any visibility into my MacApp
- derived class functions.
-
- Is this like what you encounter? Any more advice? Thanks in advance.
-
- Kenner Stross
- Please respond to x1783
-
-